{AKS} Vendor new SDK and bump API version to 2025-08-01#32242
{AKS} Vendor new SDK and bump API version to 2025-08-01#32242
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Azure Kubernetes Service (AKS) management SDK to version 40.0.0 and bumps the API version from 2025-07-01 to 2025-08-01. The changes are focused on upgrading to the latest AKS SDK version to access new features and improvements.
- Updated azure-mgmt-containerservice dependency from ~39.1.0 to ~40.0.0
- Bumped API version from 2025-07-01 to 2025-08-01 across all test recordings
- Updated version constraints consistently across all platform-specific requirement files
Reviewed Changes
Copilot reviewed 141 out of 206 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| setup.py | Updated azure-mgmt-containerservice dependency to ~40.0.0 |
| requirements.py3.*.txt | Updated azure-mgmt-containerservice to 40.0.0 for all platforms |
| test recordings | Updated API version from 2025-07-01 to 2025-08-01 in all test recordings |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
3e20812 to
edad3dd
Compare
Related command
Description
{AKS} Vendor new SDK and bump API version to 2025-08-01
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.